cannot log into the Lync Administration Control Panel > Cannot find any global catalogs
I cannot log into the Lync Administration Control Panel or admin URL.  It worked initially but now fails with :Cannot
Remote PowerShell cannot create InitialSessionState for user: .... Cause of failure: Cannot find any global catalogs in forest....
Cause: Remote PowerShell can fail to create InitialSessionState for varied number of reasons. Please look for other events that can give some specific information.
Resolution:
Follow the resolution on the corresponding failure events.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="LS Remote PowerShell" />

Some new domain controllers have been added recently.
May 13th, 2013 12:01pm

Hi

Please try to check if you are able to connect to the DC first form the Lync server.

Free Windows Admin Tool Kit Click here and download it now
May 13th, 2013 12:16pm

I can ping both domain controllers in the site.
May 13th, 2013 1:23pm

Run the Lync Deployment Wizard from the Lync server and check if "Prepare Active Directory" is still shown as Complete.



Free Windows Admin Tool Kit Click here and download it now
May 13th, 2013 2:14pm

Run the Lync Deployment Wizard from the Lync server and check if "Prepare Active Directory" is still shown as Complete.



May 13th, 2013 2:14pm

Run the Lync Deployment Wizard from the Lync server and check if "Prepare Active Directory" is still shown as Complete.



Free Windows Admin Tool Kit Click here and download it now
May 13th, 2013 2:14pm

Run the Lync Deployment Wizard from the Lync server and check if "Prepare Active Directory" is still shown as Complete.



May 13th, 2013 2:14pm

When I run the Lync 2010 Deployment Wizard it indicates that Prepare Active Directory is not completed.  This was run successfully in the past.  When I open the Active Directory Preparation' View, an error is returned under Prepare Schema:  Not Available:  Failure occurred while attempting to check the schema state.  Please ensure Active Directory is reachable.
  • Edited by vtrevor Monday, May 13, 2013 3:23 PM
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2013 3:19pm

When I run the Lync 2010 Deployment Wizard it indicates that Prepare Active Directory is not completed.  This was run successfully in the past.  When I open the Active Directory Preparation' View, an error is returned under Prepare Schema:  Not Available:  Failure occurred while attempting to check the schema state.  Please ensure Active Directory is reachable.
  • Edited by vtrevor Monday, May 13, 2013 3:23 PM
May 13th, 2013 3:19pm

When I run the Lync 2010 Deployment Wizard it indicates that Prepare Active Directory is not completed.  This was run successfully in the past.  When I open the Active Directory Preparation' View, an error is returned under Prepare Schema:  Not Available:  Failure occurred while attempting to check the schema state.  Please ensure Active Directory is reachable.
  • Edited by vtrevor Monday, May 13, 2013 3:23 PM
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2013 3:19pm

When I run the Lync 2010 Deployment Wizard it indicates that Prepare Active Directory is not completed.  This was run successfully in the past.  When I open the Active Directory Preparation' View, an error is returned under Prepare Schema:  Not Available:  Failure occurred while attempting to check the schema state.  Please ensure Active Directory is reachable.
  • Edited by vtrevor Monday, May 13, 2013 3:23 PM
May 13th, 2013 3:19pm

Run again the Prepare Active Directory form Deployment Wizard. and then try to access the Control Panel.
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2013 3:22pm

PS C:\Windows\system32> nslookup
Default Server:  ...
Address:  ...

> set q=srv
> _ldap._tcp.dc._msdcs.domain

Above returns the domain controllers

http://technet.microsoft.com/en-us/library/cc738991(v=ws.10).aspx


  • Edited by vtrevor Monday, May 13, 2013 3:37 PM
May 13th, 2013 3:37pm

PS C:\Windows\system32> nslookup
Default Server:  ...
Address:  ...

> set q=srv
> _ldap._tcp.dc._msdcs.domain

Above returns the domain controllers

http://technet.microsoft.com/en-us/library/cc738991(v=ws.10).aspx


  • Edited by vtrevor Monday, May 13, 2013 3:37 PM
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2013 3:37pm

PS C:\Windows\system32> nslookup
Default Server:  ...
Address:  ...

> set q=srv
> _ldap._tcp.dc._msdcs.domain

Above returns the domain controllers

http://technet.microsoft.com/en-us/library/cc738991(v=ws.10).aspx


  • Edited by vtrevor Monday, May 13, 2013 3:37 PM
May 13th, 2013 3:37pm

PS C:\Windows\system32> nslookup
Default Server:  ...
Address:  ...

> set q=srv
> _ldap._tcp.dc._msdcs.domain

Above returns the domain controllers

http://technet.microsoft.com/en-us/library/cc738991(v=ws.10).aspx


  • Edited by vtrevor Monday, May 13, 2013 3:37 PM
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2013 3:37pm

Hi

Did you try to run again the Prepare active Directory. That should resolve your issues

May 14th, 2013 6:55am

Please run the commands below to check you can see the GC server.

nslookup

>set q=any

>gc._msdcs.<domain>

 Check if there are any errors on DC on which the GC lies.

Free Windows Admin Tool Kit Click here and download it now
May 14th, 2013 9:29am

The issue was a firewall between the Lync FE server and the new Active directory domain controllers.  A rule update resolved the issue.
  • Marked as answer by vtrevor Monday, May 20, 2013 2:29 PM
May 20th, 2013 2:29pm

The issue was a firewall between the Lync FE server and the new Active directory domain controllers.  A rule update resolved the issue.
  • Marked as answer by vtrevor Monday, May 20, 2013 2:29 PM
Free Windows Admin Tool Kit Click here and download it now
May 20th, 2013 2:29pm

The issue was a firewall between the Lync FE server and the new Active directory domain controllers.  A rule update resolved the issue.
  • Marked as answer by vtrevor Monday, May 20, 2013 2:29 PM
May 20th, 2013 2:29pm

The issue was a firewall between the Lync FE server and the new Active directory domain controllers.  A rule update resolved the issue.
  • Marked as answer by vtrevor Monday, May 20, 2013 2:29 PM
Free Windows Admin Tool Kit Click here and download it now
May 20th, 2013 2:29pm

i have the same issue on my side.what did you do with your firewall?

on the machines i disabled them, i opened everythink to everywhere, but still no luck.

Ciao

Pascal

April 24th, 2015 5:00am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics